Rough outline of general v12 blog post #1130
Conversation
Deploying rescript-lang-org with
|
| Latest commit: |
5bc85d5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c1e9645f.rescript-lang.pages.dev |
| Branch Preview URL: | https://v12-post.rescript-lang.pages.dev |
|
This is quite good already. Not sure if we can do without all those OCaml mentions. But I think it's not relevant to the user on whatever OCaml version we build the compiler. Also not sure about the sponsorship stuff. Earlier this year I wanted to implement a Stripe form but somehow never could verify correctly with them as a representative of the ReScript Association. Maybe we should just drop the email: Also: you want to release on the 17th already? |
I don't think we need a grand plan first to mention that people can get in touch with us.
Not really, this is just a date in the future for now. |
| Examples include `Option.getOrThrow`, `List.headOrThrow`, `BigInt.fromStringOrThrow`, and `JSON.parseOrThrow`. | ||
| The change clarifies that these functions throw JavaScript errors, aligning the naming with the language’s semantics. | ||
| The deprecated `*Exn` variants remain available in v12 to ease the transition, and the codemod bundled with the migration tool can perform a mechanical rename. | ||
| Be aware that `Result.getOrThrow` now throws a JavaScript `Error`, so update any exception handling logic that depended on OCaml exception names. |
There was a problem hiding this comment.
while we're there, we should likely also mention the rework of JS exceptions from Exn.Error(Error.t) to JsExn(unknown) to better model JS exception payloads that can be of any type and potentially not Errors.
There was a problem hiding this comment.
@tsnobip as you are like the architecture of this devilry, would you mind tossing in a line here?
No description provided.